Sourced from rich-domain's releases.

v1.25.1

What's Changed

• Release/v1.25.0 by @​4lessandrodev in 4lessandrodev/rich-domain#204

Full Changelog: 4lessandrodev/rich-domain@v1.25.0...v1.25.1

Sourced from rich-domain's changelog.

[1.25.1] - 2024-12-20

Feat

• Dynamic Typing in Result Made Optional:
  • Developers can now choose between Result<T> (non-nullable) and Result<T | null> (nullable), based on their specific use case.
  • This update allows greater flexibility for explicit null handling without forcing unnecessary complexity in scenarios where nullability is not required.

Examples

1. Explicit Null Handling:
   Use Result<T | null> to manage nullable states explicitly:

   class SampleNullish {
       public static create(props: Props): Result<SampleNullish | null> {
           if (!props.name || props.name.trim() === '') {
               return Fail('name is required');
           }
           return Ok(new SampleNullish(props));
       }
   }

2. Non-Nullable Values:
   Use Result<T> for cases where null handling is unnecessary:

   class Sample {
       public static create(props: Props): Result<Sample> {
           if (!props.name || props.name.trim() === '') {
               return Fail('name is required');
           }
           return Ok(new Sample(props));
       }
   }

Fix

• Enhanced backward compatibility by making nullable typing optional, ensuring existing integrations using Result<T> remain unaffected.

Impact

• Improved Flexibility:
  Developers can adapt the Result type to suit their needs, supporting nullable and non-nullable use cases seamlessly.

• Enhanced Clarity:
  Provides explicit type inference, ensuring safer and more intuitive code handling for nullable scenarios.

---

• 003cfd7 docs: update version
• a01d616 fix: ensure tests for revert #194
• 355abf3 fix: revert type instance or null to Result #194
• 78b5424 fix: revert type instance or null to Fail #194
• d3623a3 fix: revert type instance or null to adapter #194
• 5958792 Merge pull request #204 from 4lessandrodev/release/v1.25.0
• See full diff in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)